home *** CD-ROM | disk | FTP | other *** search
- Path: fido.asd.sgi.com!austern
- From: David Byrden <100101.2547@compuserve.com>
- Newsgroups: comp.std.c++
- Subject: Why no allocator-specific delete?
- Date: 22 Jan 1996 09:46:59 PST
- Organization: self-employed
- Approved: austern@isolde.mti.sgi.com
- Message-ID: <4dvid8$460@news.bridge.net>
- NNTP-Posting-Host: isolde.mti.sgi.com
- X-Original-Date: 22 Jan 1996 08:38:00 GMT
- X-Mailer: Mozilla 1.1N (Windows; I; 16bit)
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBVAwUBMQPNq0y4NqrwXLNJAQFF8wH/S10X8LGQWqJWUTH0G31F7py3pabRpgaP
- EeBRnhcbRgv9vSAKelnbiJgxaXgfKA6RgwITG6E6E8045Q8Uo4vqqw==
- =YmOK
- Originator: austern@isolde.mti.sgi.com
-
- Why, in the Septenber draft standard, is an allocator-specific verrion of
- 'new' provided;
-
- 20.1.4.4
-
- new(x) T
-
- returns an X::types<T>::pointer, where x is of an
- allocator type X
-
-
- but there is no matching version of 'delete'? Are we supposed to use both
- destroy() and deallocate() to get rid of that object?
-
-
- David
- ---
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. The moderation policy
- is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
-